home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000022_icon-group-sender_Mon Sep 9 12:25:38 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id g89JNtA02982
for icon-group-addresses; Mon, 9 Sep 2002 12:23:55 -0700 (MST)
Message-Id: <200209091923.g89JNtA02982@baskerville.CS.Arizona.EDU>
Subject: Using Procedure Names for Debugging
From: Steve Graham <Steve_Graham@labcorp.com>
To: Icon Group <icon-group@cs.arizona.edu>
Date: 09 Sep 2002 12:35:14 -0500
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
While developing an Icon program, I wanted an easy way to debug each
procedure. I had read that there is more than 1 way to invoke a
command. For example, you can have the statement write(5) or you can
have "write"(5). I figured that I would use this idea to develop a test
module, to which I would pass a procedure name and arguments. The test
module would in turn invoke the specified procedure as in the 2nd
example above with the arguments and report back the results, if any.
However, I wasn't able to make it work. I'd bet there is a way,
though. Any ideas?
TIA, Steve